Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f8e12914ab0ada1ed3dabce967652de2ba8d6809d511eeb5423cff58d406900

Tx prefix hash: 63e9958009e0d72e12c534ba6856b93758926f5cd0514d70214acb9e46247835
Tx public key: 619a14bf51482087b3b18e191852b9721f9cb3a9863051d81d21d8a2a3a7aae6
Timestamp: 1715934487 Timestamp [UCT]: 2024-05-17 08:28:07 Age [y:d:h:m:s]: 00:306:09:35:28
Block: 1023853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219012 RingCT/type: yes/0
Extra: 01619a14bf51482087b3b18e191852b9721f9cb3a9863051d81d21d8a2a3a7aae602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f91a6d2f12324c05aaee742d55a4f6329b840bdc3ab0ea2dea93d03032b3850 0.600000000000 1489140 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": 1023863, "vin": [ { "gen": { "height": 1023853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f91a6d2f12324c05aaee742d55a4f6329b840bdc3ab0ea2dea93d03032b3850" } } ], "extra": [ 1, 97, 154, 20, 191, 81, 72, 32, 135, 179, 177, 142, 25, 24, 82, 185, 114, 31, 156, 179, 169, 134, 48, 81, 216, 29, 33, 216, 162, 163, 167, 170, 230, 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