Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ba39016ca264d206cbc4130637d8fed404920da2c39f6dff5427d671ee1ff8

Tx prefix hash: 47a71181f1038f244daa49ad11bf778e0bb0f9e7221ba09ee02afb342eead34a
Tx public key: bdd2c00e769c0857bcbaa89f73c8006f987e6e5021f7c7863f8349063f00e5a5
Timestamp: 1706250111 Timestamp [UCT]: 2024-01-26 06:21:51 Age [y:d:h:m:s]: 01:311:17:05:23
Block: 943532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481633 RingCT/type: yes/0
Extra: 01bdd2c00e769c0857bcbaa89f73c8006f987e6e5021f7c7863f8349063f00e5a502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b349123f27021e62fc253cb6c424b4dc1ccd76a0d805a717e71e7ba0db476f 0.600000000000 1401740 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": 943542, "vin": [ { "gen": { "height": 943532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b349123f27021e62fc253cb6c424b4dc1ccd76a0d805a717e71e7ba0db476f" } } ], "extra": [ 1, 189, 210, 192, 14, 118, 156, 8, 87, 188, 186, 168, 159, 115, 200, 0, 111, 152, 126, 110, 80, 33, 247, 199, 134, 63, 131, 73, 6, 63, 0, 229, 165, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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