Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed5ce41c78c830153ecdae716b03281932b4e4a92bcffd8aed1469fc2a2692e5

Tx prefix hash: dc7b22a5e361c1c010f188439ce547f5ce42d44932a640819a91fe40903d2b48
Tx public key: 7ef8ebdcabe91c80a4b141be76720079fb7c59c4c3a013ae57b72a40ce01f18d
Timestamp: 1710004696 Timestamp [UCT]: 2024-03-09 17:18:16 Age [y:d:h:m:s]: 01:063:18:30:46
Block: 974698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306587 RingCT/type: yes/0
Extra: 017ef8ebdcabe91c80a4b141be76720079fb7c59c4c3a013ae57b72a40ce01f18d02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f16d67402399a8400ed053d6610a88f090018ae5c3a49140c44dc90049326849 0.600000000000 1434657 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": 974708, "vin": [ { "gen": { "height": 974698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f16d67402399a8400ed053d6610a88f090018ae5c3a49140c44dc90049326849" } } ], "extra": [ 1, 126, 248, 235, 220, 171, 233, 28, 128, 164, 177, 65, 190, 118, 114, 0, 121, 251, 124, 89, 196, 195, 160, 19, 174, 87, 183, 42, 64, 206, 1, 241, 141, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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