Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01913a696c3e39a1411789082ec931f33a126c407ec80b684afa1ed73527f3e6

Tx prefix hash: f051ce55ffd850cccec108425b0f11a702c1a3ec591ed802c501e29f65d09aa6
Tx public key: 725d07f936a0b176888b48e8fa8bb4a6f423674a95634ad29d7e5a90838dffb1
Timestamp: 1728342158 Timestamp [UCT]: 2024-10-07 23:02:38 Age [y:d:h:m:s]: 00:197:22:43:49
Block: 1126721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141264 RingCT/type: yes/0
Extra: 01725d07f936a0b176888b48e8fa8bb4a6f423674a95634ad29d7e5a90838dffb102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 038242ead1d9c2adadde341c2c6abe139d953da8d1f10f0a7f8e4e168c005e79 0.600000000000 1609516 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": 1126731, "vin": [ { "gen": { "height": 1126721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "038242ead1d9c2adadde341c2c6abe139d953da8d1f10f0a7f8e4e168c005e79" } } ], "extra": [ 1, 114, 93, 7, 249, 54, 160, 177, 118, 136, 139, 72, 232, 250, 139, 180, 166, 244, 35, 103, 74, 149, 99, 74, 210, 157, 126, 90, 144, 131, 141, 255, 177, 2, 17, 0, 0, 0, 2, 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