Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0badbc599cb230b1795a840f9a9ae166ff461fbfb52ded06a95079cd3c8744e

Tx prefix hash: 790f2edb5276d86d43cff9b01e09482766f6d37875f8e0a7b166e09339cc96d9
Tx public key: 42594a37a78d8fa08808f223f99bb33dfa4f738ebb1eeb90a0280455dbf1c3a5
Timestamp: 1729757380 Timestamp [UCT]: 2024-10-24 08:09:40 Age [y:d:h:m:s]: 01:017:06:34:50
Block: 1138416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270737 RingCT/type: yes/0
Extra: 0142594a37a78d8fa08808f223f99bb33dfa4f738ebb1eeb90a0280455dbf1c3a50211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df3f126c7a06a3af66cc9f44b91f0d723a04bd179289f30b77b57f4718c4eb95 0.600000000000 1622083 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": 1138426, "vin": [ { "gen": { "height": 1138416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df3f126c7a06a3af66cc9f44b91f0d723a04bd179289f30b77b57f4718c4eb95" } } ], "extra": [ 1, 66, 89, 74, 55, 167, 141, 143, 160, 136, 8, 242, 35, 249, 155, 179, 61, 250, 79, 115, 142, 187, 30, 235, 144, 160, 40, 4, 85, 219, 241, 195, 165, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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