Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 919ae54e546f5b247168c681fc700883bf958b44adda6c5580d434b0fa9dfbab

Tx prefix hash: 4f58b513ed5c092fc58ef610cb3c64a1a603ebda2c7f8d41e8edd01577b89eb3
Tx public key: f98bc920820669b9393853474fb48e8367faf9a7b8eed1a10fe50a4924d9e8a7
Timestamp: 1727084260 Timestamp [UCT]: 2024-09-23 09:37:40 Age [y:d:h:m:s]: 00:265:20:16:11
Block: 1116282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189769 RingCT/type: yes/0
Extra: 01f98bc920820669b9393853474fb48e8367faf9a7b8eed1a10fe50a4924d9e8a7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36ae0d608995ac7b539faffc0d1e5dbb3f2fa0b935cfb446ea2891155eed1d51 0.600000000000 1596713 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": 1116292, "vin": [ { "gen": { "height": 1116282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36ae0d608995ac7b539faffc0d1e5dbb3f2fa0b935cfb446ea2891155eed1d51" } } ], "extra": [ 1, 249, 139, 201, 32, 130, 6, 105, 185, 57, 56, 83, 71, 79, 180, 142, 131, 103, 250, 249, 167, 184, 238, 209, 161, 15, 229, 10, 73, 36, 217, 232, 167, 2, 17, 0, 0, 0, 6, 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