Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b58c781305b82dcbe18e61fbba8e4998aa4550085289c42f63411fa75ac694b6

Tx prefix hash: 3efb3a32d48aa435bda2007cf4f2c413a21c63ffa5f8a50c487571e7b0728b23
Tx public key: 61f1432e01ffc4e718a5a171e3f61339dec9d92aa9a70d888bc0b55b87a4c243
Timestamp: 1734254275 Timestamp [UCT]: 2024-12-15 09:17:55 Age [y:d:h:m:s]: 00:097:00:09:51
Block: 1175637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69107 RingCT/type: yes/0
Extra: 0161f1432e01ffc4e718a5a171e3f61339dec9d92aa9a70d888bc0b55b87a4c2430211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 832c9a6a96344355c47600ae0a7bad09cca90d8061d1d47d1f3cc66924f8b020 0.600000000000 1661944 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": 1175647, "vin": [ { "gen": { "height": 1175637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "832c9a6a96344355c47600ae0a7bad09cca90d8061d1d47d1f3cc66924f8b020" } } ], "extra": [ 1, 97, 241, 67, 46, 1, 255, 196, 231, 24, 165, 161, 113, 227, 246, 19, 57, 222, 201, 217, 42, 169, 167, 13, 136, 139, 192, 181, 91, 135, 164, 194, 67, 2, 17, 0, 0, 0, 3, 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