Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce243cd8ce0ac22c9444bda9a436e3b725cae71068373e54d27f6bb212474c07

Tx prefix hash: 6e0e42080a88c5e065821f4e745ab3b779a0152a2318d5e1b50e5c80de5fea81
Tx public key: e74a6d4748bca37dd8999733d694e4b6ed72b29ce1f23cb2fcfadd4c39565d07
Timestamp: 1725213502 Timestamp [UCT]: 2024-09-01 17:58:22 Age [y:d:h:m:s]: 00:228:20:49:08
Block: 1100785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163428 RingCT/type: yes/0
Extra: 01e74a6d4748bca37dd8999733d694e4b6ed72b29ce1f23cb2fcfadd4c39565d07021100000012e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 669a2a3230b813c4aaeae17b78bf385a6f2eb546845c50712b5563317d167c4d 0.600000000000 1576766 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": 1100795, "vin": [ { "gen": { "height": 1100785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "669a2a3230b813c4aaeae17b78bf385a6f2eb546845c50712b5563317d167c4d" } } ], "extra": [ 1, 231, 74, 109, 71, 72, 188, 163, 125, 216, 153, 151, 51, 214, 148, 228, 182, 237, 114, 178, 156, 225, 242, 60, 178, 252, 250, 221, 76, 57, 86, 93, 7, 2, 17, 0, 0, 0, 18, 233, 20, 221, 21, 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