Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14e71d72c1ed5352af4c8778ae216c8369c948597fb47c4a88431556fdf800f9

Tx prefix hash: 1e641331d441474d98777f6c95f50acad4e4f4356bfd34d097ef57ec2b3c85e8
Tx public key: 1fc20bf3ec70b3e73d1396860fade57b9afdf86a53556ed4868f81ff5d2c9f1f
Timestamp: 1727324572 Timestamp [UCT]: 2024-09-26 04:22:52 Age [y:d:h:m:s]: 00:195:10:34:07
Block: 1118284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139490 RingCT/type: yes/0
Extra: 011fc20bf3ec70b3e73d1396860fade57b9afdf86a53556ed4868f81ff5d2c9f1f02110000001591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bb3d4fea2f39faa605f98a234bd95675d6b221c9639e730fbac06c1d14f2428 0.600000000000 1599423 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": 1118294, "vin": [ { "gen": { "height": 1118284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bb3d4fea2f39faa605f98a234bd95675d6b221c9639e730fbac06c1d14f2428" } } ], "extra": [ 1, 31, 194, 11, 243, 236, 112, 179, 231, 61, 19, 150, 134, 15, 173, 229, 123, 154, 253, 248, 106, 83, 85, 110, 212, 134, 143, 129, 255, 93, 44, 159, 31, 2, 17, 0, 0, 0, 21, 145, 225, 60, 4, 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