Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb15b03ffa1dd421d662568c6eed23549f692cc92aa87387942730f7db6c7435

Tx prefix hash: ec2bdc24ecc70a8faf51da3e2a46479a62cd9368b7c4283adca43faf207a9a05
Tx public key: 964059ae2e545f11f2bedfd3e27b45cb1e6304bd79e32a16a725903411510ad9
Timestamp: 1724076916 Timestamp [UCT]: 2024-08-19 14:15:16 Age [y:d:h:m:s]: 00:249:08:47:29
Block: 1091361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178080 RingCT/type: yes/0
Extra: 01964059ae2e545f11f2bedfd3e27b45cb1e6304bd79e32a16a725903411510ad902110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 838af037b131231d790c35f4dc704e1e6b2de16cdd137a478d2118d032c6a6ac 0.600000000000 1565992 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": 1091371, "vin": [ { "gen": { "height": 1091361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "838af037b131231d790c35f4dc704e1e6b2de16cdd137a478d2118d032c6a6ac" } } ], "extra": [ 1, 150, 64, 89, 174, 46, 84, 95, 17, 242, 190, 223, 211, 226, 123, 69, 203, 30, 99, 4, 189, 121, 227, 42, 22, 167, 37, 144, 52, 17, 81, 10, 217, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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