Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ecb6d2c40aea0df3996d152011f8f30e301d9348b5fc3ec24cd273118d5c42

Tx prefix hash: 353c175b21568062c69ae27c81968d15fd1fb71c5fec810e1ca2c16b1acfcbea
Tx public key: bb36b4ce3c07ce8528a3a1950a9875446e9c2a6d4fc5a05a7993a146bf63e8f8
Timestamp: 1701506048 Timestamp [UCT]: 2023-12-02 08:34:08 Age [y:d:h:m:s]: 01:083:07:38:16
Block: 904225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320664 RingCT/type: yes/0
Extra: 01bb36b4ce3c07ce8528a3a1950a9875446e9c2a6d4fc5a05a7993a146bf63e8f80211000000034b8f5122000000000000000000

1 output(s) for total of 0.619337234000 dcy

stealth address amount amount idx
00: 1d3e7c6cab797fba0740b1ecffc3580f1a7322ea4abde375410326c4931e1d26 0.619337234000 1360940 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": 904235, "vin": [ { "gen": { "height": 904225 } } ], "vout": [ { "amount": 619337234, "target": { "key": "1d3e7c6cab797fba0740b1ecffc3580f1a7322ea4abde375410326c4931e1d26" } } ], "extra": [ 1, 187, 54, 180, 206, 60, 7, 206, 133, 40, 163, 161, 149, 10, 152, 117, 68, 110, 156, 42, 109, 79, 197, 160, 90, 121, 147, 161, 70, 191, 99, 232, 248, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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