Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a8b90b6cd65aa9dcdf22e27bc6cff7cfc806251eac823f2148554bef8eb1e1b

Tx prefix hash: 57a8ec9e9d8e915668fbf65934e3a655d961e673a4beaec0e574659e4e6e956c
Tx public key: 8187b736617a1bbf89f520cb631351e553003cd33653c5e8251a4032afa472f0
Timestamp: 1723734916 Timestamp [UCT]: 2024-08-15 15:15:16 Age [y:d:h:m:s]: 00:306:15:44:58
Block: 1088524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218971 RingCT/type: yes/0
Extra: 018187b736617a1bbf89f520cb631351e553003cd33653c5e8251a4032afa472f0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b3e5b3dff3d9b3ac4bbc253ced9155dfdd9ef2f29567f826ce87d42bdf2c614 0.600000000000 1563141 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": 1088534, "vin": [ { "gen": { "height": 1088524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b3e5b3dff3d9b3ac4bbc253ced9155dfdd9ef2f29567f826ce87d42bdf2c614" } } ], "extra": [ 1, 129, 135, 183, 54, 97, 122, 27, 191, 137, 245, 32, 203, 99, 19, 81, 229, 83, 0, 60, 211, 54, 83, 197, 232, 37, 26, 64, 50, 175, 164, 114, 240, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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