Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bea658537b9e2dc12563df8cd8ac1dde807c9f1412809cd3f684d1d99b2f1f6

Tx prefix hash: 008f584d832ca6d5b95af4b0887af144c5e8fa44388f87c7f6bf4b02c786bf91
Tx public key: b9e2efc2c30e6d42bedc57c81b4e6ef1b60d543c2e2804cf3bc53188a8c1d88e
Timestamp: 1726846634 Timestamp [UCT]: 2024-09-20 15:37:14 Age [y:d:h:m:s]: 00:246:14:28:13
Block: 1114317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176108 RingCT/type: yes/0
Extra: 01b9e2efc2c30e6d42bedc57c81b4e6ef1b60d543c2e2804cf3bc53188a8c1d88e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d6a6c1a039ab59735564cd2abe06f2c986f6cb92157102194c45cdcc70411c6 0.600000000000 1594116 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": 1114327, "vin": [ { "gen": { "height": 1114317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d6a6c1a039ab59735564cd2abe06f2c986f6cb92157102194c45cdcc70411c6" } } ], "extra": [ 1, 185, 226, 239, 194, 195, 14, 109, 66, 190, 220, 87, 200, 27, 78, 110, 241, 182, 13, 84, 60, 46, 40, 4, 207, 59, 197, 49, 136, 168, 193, 216, 142, 2, 17, 0, 0, 0, 1, 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