Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5703e8587da5a2e4e24252e5dc002605ba626c41a2a3fcb1f1b7c77173850234

Tx prefix hash: c3010e9cb35e9fc9815a1695657b1cb9f34c7f0f8d8a051501ce8479be0cf88f
Tx public key: 7aaaf1e3fd30541d940f41772326d5bf877131597fa4e8734dd481f40c0bb5db
Timestamp: 1726587920 Timestamp [UCT]: 2024-09-17 15:45:20 Age [y:d:h:m:s]: 00:204:14:06:07
Block: 1112164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146051 RingCT/type: yes/0
Extra: 017aaaf1e3fd30541d940f41772326d5bf877131597fa4e8734dd481f40c0bb5db02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9884ff08109790c35cf7d66ca87ae45bffedfbc3824ffd6c4ce0a221c2e03dc 0.600000000000 1591389 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": 1112174, "vin": [ { "gen": { "height": 1112164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9884ff08109790c35cf7d66ca87ae45bffedfbc3824ffd6c4ce0a221c2e03dc" } } ], "extra": [ 1, 122, 170, 241, 227, 253, 48, 84, 29, 148, 15, 65, 119, 35, 38, 213, 191, 135, 113, 49, 89, 127, 164, 232, 115, 77, 212, 129, 244, 12, 11, 181, 219, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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