Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5285cd0946ae6ea5c8742fa69d775d7852af83ed68ebfbfcb0b0d47787cc91c8

Tx prefix hash: 1cc9595c9933f32d2ce5e613d478f998ae3a6543970f14c77be22b8d06d7d90e
Tx public key: c6ef83f8a70b59ddfc841693897948a73820b7deff5ee93d2b46e7385fdb4c2e
Timestamp: 1703621388 Timestamp [UCT]: 2023-12-26 20:09:48 Age [y:d:h:m:s]: 01:092:07:28:37
Block: 921767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327081 RingCT/type: yes/0
Extra: 01c6ef83f8a70b59ddfc841693897948a73820b7deff5ee93d2b46e7385fdb4c2e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e54948c8f6f59afa08a17d78adb9ed3837877a951ef4dcbe627b082378349e3f 0.600000000000 1379461 of 15

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": 921777, "vin": [ { "gen": { "height": 921767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e54948c8f6f59afa08a17d78adb9ed3837877a951ef4dcbe627b082378349e3f" } } ], "extra": [ 1, 198, 239, 131, 248, 167, 11, 89, 221, 252, 132, 22, 147, 137, 121, 72, 167, 56, 32, 183, 222, 255, 94, 233, 61, 43, 70, 231, 56, 95, 219, 76, 46, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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