Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd13bedeaf3b2f913e0f0c21cd9a555d8dd6365bfda912c21161ce7b07ce6642

Tx prefix hash: 0903a48f69c93a44a3de8b02bedab698d571c73a98822e9d48be14627d427ebc
Tx public key: aa091872dd3bd30c544cdba276c3e94668f6d26e332ce4c396ef00cb04c9b1c3
Timestamp: 1695678153 Timestamp [UCT]: 2023-09-25 21:42:33 Age [y:d:h:m:s]: 01:190:15:24:11
Block: 856116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397307 RingCT/type: yes/0
Extra: 01aa091872dd3bd30c544cdba276c3e94668f6d26e332ce4c396ef00cb04c9b1c302110000000233af99f4000000000000000000

1 output(s) for total of 0.893989358000 dcy

stealth address amount amount idx
00: 74b17e4d88c9d49ccd35eaabc0441760a210c97e9f337b26a0cc27f844272790 0.893989358000 1310174 of 0

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": 856126, "vin": [ { "gen": { "height": 856116 } } ], "vout": [ { "amount": 893989358, "target": { "key": "74b17e4d88c9d49ccd35eaabc0441760a210c97e9f337b26a0cc27f844272790" } } ], "extra": [ 1, 170, 9, 24, 114, 221, 59, 211, 12, 84, 76, 219, 162, 118, 195, 233, 70, 104, 246, 210, 110, 51, 44, 228, 195, 150, 239, 0, 203, 4, 201, 177, 195, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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