Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6a459b1711c6cb27b880a6e97710e0206c7bc648e382104a1fd2214d085cc68

Tx prefix hash: 805c1ea79d211d8b01629065c8717af1c6c5c99b5f54cf43f317c55c33396ec5
Tx public key: 84852cecf055e7b43e9b6845cbe25bea675dac8fc305deee82ead566925c7eba
Timestamp: 1737154241 Timestamp [UCT]: 2025-01-17 22:50:41 Age [y:d:h:m:s]: 00:156:03:42:05
Block: 1199620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111223 RingCT/type: yes/0
Extra: 0184852cecf055e7b43e9b6845cbe25bea675dac8fc305deee82ead566925c7eba0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e57fd15e2349c6d0ba3a5c96b773a8272363e342093d283228210d3c0262bd7 0.600000000000 1686253 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": 1199630, "vin": [ { "gen": { "height": 1199620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e57fd15e2349c6d0ba3a5c96b773a8272363e342093d283228210d3c0262bd7" } } ], "extra": [ 1, 132, 133, 44, 236, 240, 85, 231, 180, 62, 155, 104, 69, 203, 226, 91, 234, 103, 93, 172, 143, 195, 5, 222, 238, 130, 234, 213, 102, 146, 92, 126, 186, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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