Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe6e6401f384e564de56fe61f6dea11d029a4da25b4009e53d9f572357fa522

Tx prefix hash: 68705b077204ffe626a02e7c70d7bc5277a3dc41afdd292cefe2e2f6041c5306
Tx public key: e609efc564410351b8b9deb1fb42c1fbce45c6c0bef340d061ec2a2d5a41d488
Timestamp: 1728631212 Timestamp [UCT]: 2024-10-11 07:20:12 Age [y:d:h:m:s]: 00:213:06:37:20
Block: 1129114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152239 RingCT/type: yes/0
Extra: 01e609efc564410351b8b9deb1fb42c1fbce45c6c0bef340d061ec2a2d5a41d488021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6651d1fe6b75ddec9bf602131040a450c7db90d5be332ea4fafc52c9fef1540 0.600000000000 1611939 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": 1129124, "vin": [ { "gen": { "height": 1129114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6651d1fe6b75ddec9bf602131040a450c7db90d5be332ea4fafc52c9fef1540" } } ], "extra": [ 1, 230, 9, 239, 197, 100, 65, 3, 81, 184, 185, 222, 177, 251, 66, 193, 251, 206, 69, 198, 192, 190, 243, 64, 208, 97, 236, 42, 45, 90, 65, 212, 136, 2, 17, 0, 0, 0, 5, 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