Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9520e633520ea477594b71e43ca7b89b2a16a3974d5f1fa597aa5a08abca5e8

Tx prefix hash: d80ae763043d74e31ed8c7a15974b7d7866149bcafd3342f2abd1f19905256b9
Tx public key: 8028838fe8df2a0d9b0eda08c064a349b7d2177c4e8c3598ad5b9a423453be72
Timestamp: 1726758445 Timestamp [UCT]: 2024-09-19 15:07:25 Age [y:d:h:m:s]: 00:156:01:10:20
Block: 1113585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111306 RingCT/type: yes/0
Extra: 018028838fe8df2a0d9b0eda08c064a349b7d2177c4e8c3598ad5b9a423453be72021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7862165b1b5910599248ddece7608bb87610bc2bc893f08748a7803bb2f7158a 0.600000000000 1593312 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": 1113595, "vin": [ { "gen": { "height": 1113585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7862165b1b5910599248ddece7608bb87610bc2bc893f08748a7803bb2f7158a" } } ], "extra": [ 1, 128, 40, 131, 143, 232, 223, 42, 13, 155, 14, 218, 8, 192, 100, 163, 73, 183, 210, 23, 124, 78, 140, 53, 152, 173, 91, 154, 66, 52, 83, 190, 114, 2, 17, 0, 0, 0, 3, 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