Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8b1ce460495a8ec59c6925b41ac4acf12615c8892e69cbcb957fc2f7df983628

Tx prefix hash: 78ebb9e685caa68ca1d8166889aa7878bac12be406190555fe4ea090e8d90e8e
Tx public key: 3669b0691fbdd5fca8ffc81122f8f377fb1efab0293b6cdc77df4d357e59d58e
Timestamp: 1672854588 Timestamp [UCT]: 2023-01-04 17:49:48 Age [y:d:h:m:s]: 02:155:18:39:10
Block: 667562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 633071 RingCT/type: yes/0
Extra: 013669b0691fbdd5fca8ffc81122f8f377fb1efab0293b6cdc77df4d357e59d58e021100000009e6d27f9c000000000000000000

1 output(s) for total of 3.767818174000 dcy

stealth address amount amount idx
00: 0316197d1904596bb8cd2908dd3ed07f8677e61ff48c3d3c4c037fecda8b5a74 3.767818174000 1108775 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 667572, "vin": [ { "gen": { "height": 667562 } } ], "vout": [ { "amount": 3767818174, "target": { "key": "0316197d1904596bb8cd2908dd3ed07f8677e61ff48c3d3c4c037fecda8b5a74" } } ], "extra": [ 1, 54, 105, 176, 105, 31, 189, 213, 252, 168, 255, 200, 17, 34, 248, 243, 119, 251, 30, 250, 176, 41, 59, 108, 220, 119, 223, 77, 53, 126, 89, 213, 142, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8