Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c4fd7e080899d0ef11ffc12b792860e9227b43f3a234dc6411b3c4da396894d

Tx prefix hash: cd2c6339e7273979bacd53cd5d21fb764290c3148ec411dafe1716bc1e6fd9fc
Tx public key: 51306c2abd338522411ed299fab36ef56a78c889062b0f27c2f3d4b97d63512e
Timestamp: 1730631678 Timestamp [UCT]: 2024-11-03 11:01:18 Age [y:d:h:m:s]: 00:160:10:07:52
Block: 1145620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114477 RingCT/type: yes/0
Extra: 0151306c2abd338522411ed299fab36ef56a78c889062b0f27c2f3d4b97d63512e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9aa6c77d07731f76ada460c77646ce1526d14059a64aeb0daa7ae3b17c432c32 0.600000000000 1630097 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": 1145630, "vin": [ { "gen": { "height": 1145620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9aa6c77d07731f76ada460c77646ce1526d14059a64aeb0daa7ae3b17c432c32" } } ], "extra": [ 1, 81, 48, 108, 42, 189, 51, 133, 34, 65, 30, 210, 153, 250, 179, 110, 245, 106, 120, 200, 137, 6, 43, 15, 39, 194, 243, 212, 185, 125, 99, 81, 46, 2, 17, 0, 0, 0, 2, 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