Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0a25ca643819e7298f07dbd0749139825faac6a18880e47fab6952469e17d02

Tx prefix hash: dcfe4e4c4f7260090e24a0cf514c5e6b166e8bd73b2594a47247d9079e15a30a
Tx public key: 0078bda1a0e0f00a36e67974b9f02b57840ee28644f9dd3da662da6183d8a875
Timestamp: 1724606469 Timestamp [UCT]: 2024-08-25 17:21:09 Age [y:d:h:m:s]: 00:294:09:32:22
Block: 1095745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210224 RingCT/type: yes/0
Extra: 010078bda1a0e0f00a36e67974b9f02b57840ee28644f9dd3da662da6183d8a87502110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7daff5e29b5263c0b04b6b3d0d409d51907db0d501f912e296896d5efa1cbac3 0.600000000000 1570926 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": 1095755, "vin": [ { "gen": { "height": 1095745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7daff5e29b5263c0b04b6b3d0d409d51907db0d501f912e296896d5efa1cbac3" } } ], "extra": [ 1, 0, 120, 189, 161, 160, 224, 240, 10, 54, 230, 121, 116, 185, 240, 43, 87, 132, 14, 226, 134, 68, 249, 221, 61, 166, 98, 218, 97, 131, 216, 168, 117, 2, 17, 0, 0, 0, 11, 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