Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c584a49f94abac2cf24c9600054f78211ab79ba1ede5ad24d521fe01463924

Tx prefix hash: e843495e8493d14c788db3d790483470966533c96154f7bd59ba6d07abe387aa
Tx public key: e8afcf9ec49e13bca79e6969ea2bd553ade2c7afaf271f3bbd8e1e04dc77db19
Timestamp: 1696822770 Timestamp [UCT]: 2023-10-09 03:39:30 Age [y:d:h:m:s]: 02:045:12:46:44
Block: 865613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552167 RingCT/type: yes/0
Extra: 01e8afcf9ec49e13bca79e6969ea2bd553ade2c7afaf271f3bbd8e1e04dc77db1902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.831504936000 dcy

stealth address amount amount idx
00: ba7a2951b3e5f770aa1fa448fc45b0b60d8324498e1c47f30155603f7ec042cd 0.831504936000 1320151 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": 865623, "vin": [ { "gen": { "height": 865613 } } ], "vout": [ { "amount": 831504936, "target": { "key": "ba7a2951b3e5f770aa1fa448fc45b0b60d8324498e1c47f30155603f7ec042cd" } } ], "extra": [ 1, 232, 175, 207, 158, 196, 158, 19, 188, 167, 158, 105, 105, 234, 43, 213, 83, 173, 226, 199, 175, 175, 39, 31, 59, 189, 142, 30, 4, 220, 119, 219, 25, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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