Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f39c530cd5befc47ad4b9b8669a5bef771a8cd3912be492d4f78c6bb4afcd0a9

Tx prefix hash: efa79d4e0d61eb901bd3a508d550dfbc69b8a3c8759f3d9bd71ea4ed95421ac3
Tx public key: f8a60b0e334b4a6807c170c66f3aa0e764c98a9a49b3ee25dc0576833b259bb5
Timestamp: 1696702056 Timestamp [UCT]: 2023-10-07 18:07:36 Age [y:d:h:m:s]: 01:255:01:43:42
Block: 864604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443253 RingCT/type: yes/0
Extra: 01f8a60b0e334b4a6807c170c66f3aa0e764c98a9a49b3ee25dc0576833b259bb502110000000533af99f4000000000000000000

1 output(s) for total of 0.837930636000 dcy

stealth address amount amount idx
00: 41e835dac526b798cde1df9afaf14e3f22937fcfebf90aa4e2cd3c85f465fe49 0.837930636000 1319124 of 0

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": 864614, "vin": [ { "gen": { "height": 864604 } } ], "vout": [ { "amount": 837930636, "target": { "key": "41e835dac526b798cde1df9afaf14e3f22937fcfebf90aa4e2cd3c85f465fe49" } } ], "extra": [ 1, 248, 166, 11, 14, 51, 75, 74, 104, 7, 193, 112, 198, 111, 58, 160, 231, 100, 201, 138, 154, 73, 179, 238, 37, 220, 5, 118, 131, 59, 37, 155, 181, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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