Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cb48374bf253e727987f17ada433b2348d141dff63a72e64c220b51c0300391

Tx prefix hash: 52a4de8644e75b0ebe4f8c7b02e6f0a5e16529580631e7e8d5c9ce8ba0315c20
Tx public key: 466831eecc5bbeae1fb0e35a716a4b59c39dfb446cd2dbb7c1502ec112cd4af6
Timestamp: 1713346363 Timestamp [UCT]: 2024-04-17 09:32:43 Age [y:d:h:m:s]: 01:026:17:02:30
Block: 1002386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280055 RingCT/type: yes/0
Extra: 01466831eecc5bbeae1fb0e35a716a4b59c39dfb446cd2dbb7c1502ec112cd4af602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57733ea5f7489bdefa241809f08d7ff57de2a706da87ac9c5bb9969c08117664 0.600000000000 1462902 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": 1002396, "vin": [ { "gen": { "height": 1002386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57733ea5f7489bdefa241809f08d7ff57de2a706da87ac9c5bb9969c08117664" } } ], "extra": [ 1, 70, 104, 49, 238, 204, 91, 190, 174, 31, 176, 227, 90, 113, 106, 75, 89, 195, 157, 251, 68, 108, 210, 219, 183, 193, 80, 46, 193, 18, 205, 74, 246, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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