Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241a506add5812fe489930c155306c781cbe5caa1990bfb3f47b176959c747c3

Tx prefix hash: fcb74ed38b487d564ab8ba098f0d7d4a1a50f2efe99c2ef233a788306dfe0be0
Tx public key: a3f85a3325ef40e95f81d19d4f9eecc9ee1d23ff2544cf9469989920aad983a0
Timestamp: 1715801897 Timestamp [UCT]: 2024-05-15 19:38:17 Age [y:d:h:m:s]: 01:018:11:58:08
Block: 1022744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274167 RingCT/type: yes/0
Extra: 01a3f85a3325ef40e95f81d19d4f9eecc9ee1d23ff2544cf9469989920aad983a00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d67e5ecd2dc05b88a6f0e009549b7dc4807f97b15acd8c167a1ce31ace0855a 0.600000000000 1487437 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": 1022754, "vin": [ { "gen": { "height": 1022744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d67e5ecd2dc05b88a6f0e009549b7dc4807f97b15acd8c167a1ce31ace0855a" } } ], "extra": [ 1, 163, 248, 90, 51, 37, 239, 64, 233, 95, 129, 209, 157, 79, 158, 236, 201, 238, 29, 35, 255, 37, 68, 207, 148, 105, 152, 153, 32, 170, 217, 131, 160, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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