Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f306bf63fc7b53a68af3c9e68b1ef012e496353ef7423ab3da87f4ee5c6522

Tx prefix hash: e460e8694f77debdc1052952f1b3853408c74e98cc8ffdcc5a1de51e50568abe
Tx public key: 7dba45a01acde48c392ab2c83defb4fbcdba1d3d7df089e5c74ed284ba3fd3d7
Timestamp: 1711736944 Timestamp [UCT]: 2024-03-29 18:29:04 Age [y:d:h:m:s]: 00:230:05:45:32
Block: 989069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164821 RingCT/type: yes/0
Extra: 017dba45a01acde48c392ab2c83defb4fbcdba1d3d7df089e5c74ed284ba3fd3d70211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f579af4dd3343b4f01d5589698bc32d1235d73d78438fd14b8fb766af3afaba 0.600000000000 1449364 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": 989079, "vin": [ { "gen": { "height": 989069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f579af4dd3343b4f01d5589698bc32d1235d73d78438fd14b8fb766af3afaba" } } ], "extra": [ 1, 125, 186, 69, 160, 26, 205, 228, 140, 57, 42, 178, 200, 61, 239, 180, 251, 205, 186, 29, 61, 125, 240, 137, 229, 199, 78, 210, 132, 186, 63, 211, 215, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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