Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef1b4c4bf36082c84c1e6fa535794e4dde899b0b418e9732b1fbe3c922d9c7d3

Tx prefix hash: d0cb3cef4c648ded63dbc5b36def00874baf39ea212264b1fc43afbf43922fb0
Tx public key: 33aa0492291242cb940afcd0ab48889eab84914f99dd4c14fda67a5ce45d0009
Timestamp: 1706785418 Timestamp [UCT]: 2024-02-01 11:03:38 Age [y:d:h:m:s]: 01:139:12:10:39
Block: 947982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360687 RingCT/type: yes/0
Extra: 0133aa0492291242cb940afcd0ab48889eab84914f99dd4c14fda67a5ce45d00090211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0613ae4466c2f1a8840872a7dd2de13c82dccd1a9992f2296b56e986e61cc0 0.600000000000 1406348 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": 947992, "vin": [ { "gen": { "height": 947982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0613ae4466c2f1a8840872a7dd2de13c82dccd1a9992f2296b56e986e61cc0" } } ], "extra": [ 1, 51, 170, 4, 146, 41, 18, 66, 203, 148, 10, 252, 208, 171, 72, 136, 158, 171, 132, 145, 79, 153, 221, 76, 20, 253, 166, 122, 92, 228, 93, 0, 9, 2, 17, 0, 0, 0, 1, 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