Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63112a40e46bafc9f3b1c48549b551bfee6baab37593bfc84d07418bc4e347c8

Tx prefix hash: f47f68d1040dfa8278c4558b46f663f9c8cda14e75fa1fb79af74eec5865e1bb
Tx public key: b4ac1806216eb0a7b810573b897e202dceb4fc7bb096aa407c8350cc01640075
Timestamp: 1704544516 Timestamp [UCT]: 2024-01-06 12:35:16 Age [y:d:h:m:s]: 01:018:16:44:18
Block: 929396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274667 RingCT/type: yes/0
Extra: 01b4ac1806216eb0a7b810573b897e202dceb4fc7bb096aa407c8350cc0164007502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1db8b8faa7e3ce9a50255d7bf03929ae1cbf92c8e678cbc5b3a2acb0068e38d 0.600000000000 1387268 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": 929406, "vin": [ { "gen": { "height": 929396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1db8b8faa7e3ce9a50255d7bf03929ae1cbf92c8e678cbc5b3a2acb0068e38d" } } ], "extra": [ 1, 180, 172, 24, 6, 33, 110, 176, 167, 184, 16, 87, 59, 137, 126, 32, 45, 206, 180, 252, 123, 176, 150, 170, 64, 124, 131, 80, 204, 1, 100, 0, 117, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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