Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26375ec8a8d08a8916641cfdf87cd2907a29e4cf8e5982a6eebefd4bb8437a10

Tx prefix hash: 3a405cd57a8220fb1e33b8cb2b407193061ed76da2d1e785ebc0576c70bc911a
Tx public key: 6b0c7db44e8e58de3629f9c6af49d334279e3ca11f29fbc892c0cad4ab264bf7
Timestamp: 1731237830 Timestamp [UCT]: 2024-11-10 11:23:50 Age [y:d:h:m:s]: 00:141:17:26:35
Block: 1150635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101117 RingCT/type: yes/0
Extra: 016b0c7db44e8e58de3629f9c6af49d334279e3ca11f29fbc892c0cad4ab264bf70211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 599a7fbb79006635063f5bf5eaf6dd33c525bdb8c2134d7c2726abb49b8fc12d 0.600000000000 1635998 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": 1150645, "vin": [ { "gen": { "height": 1150635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "599a7fbb79006635063f5bf5eaf6dd33c525bdb8c2134d7c2726abb49b8fc12d" } } ], "extra": [ 1, 107, 12, 125, 180, 78, 142, 88, 222, 54, 41, 249, 198, 175, 73, 211, 52, 39, 158, 60, 161, 31, 41, 251, 200, 146, 192, 202, 212, 171, 38, 75, 247, 2, 17, 0, 0, 0, 1, 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