Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e625f454a369fb1d1fd610c59419fe7866232fbfee3365caf8aa5754a795be

Tx prefix hash: cce2d1dca281044864212ae91ab42cdb61a602b7665e8ccc4ba821632fb2b210
Tx public key: 263f9d8ad6a3c44b63663ddff564c6178c45fa6fe2428180b3cedecb415b6078
Timestamp: 1728748189 Timestamp [UCT]: 2024-10-12 15:49:49 Age [y:d:h:m:s]: 00:172:00:45:10
Block: 1130079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122734 RingCT/type: yes/0
Extra: 01263f9d8ad6a3c44b63663ddff564c6178c45fa6fe2428180b3cedecb415b607802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39c1bff97c98302d0a5e2e4c976177196cfdb6ddc24c0cb43774488d41e9d3f4 0.600000000000 1612950 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": 1130089, "vin": [ { "gen": { "height": 1130079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39c1bff97c98302d0a5e2e4c976177196cfdb6ddc24c0cb43774488d41e9d3f4" } } ], "extra": [ 1, 38, 63, 157, 138, 214, 163, 196, 75, 99, 102, 61, 223, 245, 100, 198, 23, 140, 69, 250, 111, 226, 66, 129, 128, 179, 206, 222, 203, 65, 91, 96, 120, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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