Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 518572c12c5ff2517386b49ff0faa3f24deffed445431c88c8a7a55ee06f9ab3

Tx prefix hash: 145acecb40491949774872b669d4c18eb7548a8a8451e5e12a5f0a284eae0474
Tx public key: f5e05a157e4530da7c8862f69ff275bad0b5abe962b6bbee9929c7c53ea2b79f
Timestamp: 1712007218 Timestamp [UCT]: 2024-04-01 21:33:38 Age [y:d:h:m:s]: 01:052:23:14:26
Block: 991263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298881 RingCT/type: yes/0
Extra: 01f5e05a157e4530da7c8862f69ff275bad0b5abe962b6bbee9929c7c53ea2b79f02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d91715f9b4b23a6ac44f5387487bd9412171fd355dfecd144322508d925e2c7c 0.600000000000 1451597 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": 991273, "vin": [ { "gen": { "height": 991263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d91715f9b4b23a6ac44f5387487bd9412171fd355dfecd144322508d925e2c7c" } } ], "extra": [ 1, 245, 224, 90, 21, 126, 69, 48, 218, 124, 136, 98, 246, 159, 242, 117, 186, 208, 181, 171, 233, 98, 182, 187, 238, 153, 41, 199, 197, 62, 162, 183, 159, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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