Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ff09c3bc737bb7e8c866312925e170e5d46b37b96e3f158df139d9a8ca9c03

Tx prefix hash: 57ec657da73c6ca56b52518cf76eee8d4a80344c8a5e721915a668036fa74010
Tx public key: 9d68fadec0c1a0ab7b0a91c44affc98067457d2db61e11b0f917d25964aab1ac
Timestamp: 1709338088 Timestamp [UCT]: 2024-03-02 00:08:08 Age [y:d:h:m:s]: 00:328:06:34:41
Block: 969169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234944 RingCT/type: yes/0
Extra: 019d68fadec0c1a0ab7b0a91c44affc98067457d2db61e11b0f917d25964aab1ac0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b29e3d607d956579cbeba975355beeea19eb510b8bde27603b926d73842b886d 0.600000000000 1428998 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": 969179, "vin": [ { "gen": { "height": 969169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b29e3d607d956579cbeba975355beeea19eb510b8bde27603b926d73842b886d" } } ], "extra": [ 1, 157, 104, 250, 222, 192, 193, 160, 171, 123, 10, 145, 196, 74, 255, 201, 128, 103, 69, 125, 45, 182, 30, 17, 176, 249, 23, 210, 89, 100, 170, 177, 172, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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