Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 897f92d59840593cc054cf13e85e320c3c8cfeb543c2590d9b3d1a5ee2c7c7e9

Tx prefix hash: 2a99717f3db83fb956a1b240f172d5e24c41e3093180fba66c8f793c4827e679
Tx public key: 94c8a61e72b7598cff97103d46c74b0bdb310d2701819d4a4de2dd45be1c131f
Timestamp: 1714990466 Timestamp [UCT]: 2024-05-06 10:14:26 Age [y:d:h:m:s]: 00:178:01:14:23
Block: 1016024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127461 RingCT/type: yes/0
Extra: 0194c8a61e72b7598cff97103d46c74b0bdb310d2701819d4a4de2dd45be1c131f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f35aa0e2f7295a148beed1fe79a1439df7e0d5b70212087cc470d7070996647 0.600000000000 1479489 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": 1016034, "vin": [ { "gen": { "height": 1016024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f35aa0e2f7295a148beed1fe79a1439df7e0d5b70212087cc470d7070996647" } } ], "extra": [ 1, 148, 200, 166, 30, 114, 183, 89, 140, 255, 151, 16, 61, 70, 199, 75, 11, 219, 49, 13, 39, 1, 129, 157, 74, 77, 226, 221, 69, 190, 28, 19, 31, 2, 17, 0, 0, 0, 1, 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