Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d50ad7afa2929051621d0b264aa8951f25c7f8a65e0198da4d602460b837ae6d

Tx prefix hash: 0048f2a6dfcff5bc3fca85385f2304129c990e1c2caf3eb90415afe344067b47
Tx public key: 0a65599a50fb51356050f7cd522077b5a02bf66e70132373b0e298c4c8a1a56f
Timestamp: 1722087374 Timestamp [UCT]: 2024-07-27 13:36:14 Age [y:d:h:m:s]: 00:241:20:21:57
Block: 1074863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172739 RingCT/type: yes/0
Extra: 010a65599a50fb51356050f7cd522077b5a02bf66e70132373b0e298c4c8a1a56f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94fe757d6cce4cbb8972a2aa18ae38ebea70266adbb8325423a2ae10d9e0f404 0.600000000000 1547382 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": 1074873, "vin": [ { "gen": { "height": 1074863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94fe757d6cce4cbb8972a2aa18ae38ebea70266adbb8325423a2ae10d9e0f404" } } ], "extra": [ 1, 10, 101, 89, 154, 80, 251, 81, 53, 96, 80, 247, 205, 82, 32, 119, 181, 160, 43, 246, 110, 112, 19, 35, 115, 176, 226, 152, 196, 200, 161, 165, 111, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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