Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1610925470335592c9e478f649349d6d35c189d58173d90dca6ed8503f29db78

Tx prefix hash: f5240d281a0a1c9fde92b14f2b519cf9d0f61b6bc0823c44d81eb5c93c6b7ce7
Tx public key: 67e80ffcfec7e90256a40fc8ab583e58e42c3b9a588d20cb32016c3f1d43f77b
Timestamp: 1736209357 Timestamp [UCT]: 2025-01-07 00:22:37 Age [y:d:h:m:s]: 00:080:08:28:16
Block: 1191794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57214 RingCT/type: yes/0
Extra: 0167e80ffcfec7e90256a40fc8ab583e58e42c3b9a588d20cb32016c3f1d43f77b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae133d594b0110c827124c6088f70eba3fe33267b61999d2ade3f25cfdeb4fb1 0.600000000000 1678335 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": 1191804, "vin": [ { "gen": { "height": 1191794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae133d594b0110c827124c6088f70eba3fe33267b61999d2ade3f25cfdeb4fb1" } } ], "extra": [ 1, 103, 232, 15, 252, 254, 199, 233, 2, 86, 164, 15, 200, 171, 88, 62, 88, 228, 44, 59, 154, 88, 141, 32, 203, 50, 1, 108, 63, 29, 67, 247, 123, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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