Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 196385c0cb07101a81a6ddae584b0dc65fa96e027d19347bf42a525939226978

Tx prefix hash: 65963742634f0de0c6a649014737b3efa948b1693129265a1a3b3c317177ec84
Tx public key: 839fe68cbc5f4b75ea8c4886e557d423eb668ea0c90de9bcc5eef2722aa2d064
Timestamp: 1721112417 Timestamp [UCT]: 2024-07-16 06:46:57 Age [y:d:h:m:s]: 01:153:21:55:09
Block: 1066790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368541 RingCT/type: yes/0
Extra: 01839fe68cbc5f4b75ea8c4886e557d423eb668ea0c90de9bcc5eef2722aa2d06402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 956a1d2022706db712994815a4ded67d1d1477309b3dbee0b9322e93efd7380d 0.600000000000 1537457 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": 1066800, "vin": [ { "gen": { "height": 1066790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "956a1d2022706db712994815a4ded67d1d1477309b3dbee0b9322e93efd7380d" } } ], "extra": [ 1, 131, 159, 230, 140, 188, 95, 75, 117, 234, 140, 72, 134, 229, 87, 212, 35, 235, 102, 142, 160, 201, 13, 233, 188, 197, 238, 242, 114, 42, 162, 208, 100, 2, 17, 0, 0, 0, 3, 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