Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6d0c04803fd2f43b9d89e998843391536349ef4e1c81bfebe0385bb922959d

Tx prefix hash: 6fe89a4fc3dbc473e9a690f8ab2c9189c35a1510deeb759e6cef9968c6190801
Tx public key: 1b1c9e8ea559ad80d53f11f0fa57d4b0d206c3bd243dec49ac3734b68298dc9d
Timestamp: 1697419975 Timestamp [UCT]: 2023-10-16 01:32:55 Age [y:d:h:m:s]: 01:185:04:11:08
Block: 870556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393380 RingCT/type: yes/0
Extra: 011b1c9e8ea559ad80d53f11f0fa57d4b0d206c3bd243dec49ac3734b68298dc9d021100000002faf35c9c000000000000000000

1 output(s) for total of 0.800730947000 dcy

stealth address amount amount idx
00: a4e12743d5d64db2dea1a592fdb76e3f6fdddb8ba99f0d67e9a460b36a22b064 0.800730947000 1325439 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": 870566, "vin": [ { "gen": { "height": 870556 } } ], "vout": [ { "amount": 800730947, "target": { "key": "a4e12743d5d64db2dea1a592fdb76e3f6fdddb8ba99f0d67e9a460b36a22b064" } } ], "extra": [ 1, 27, 28, 158, 142, 165, 89, 173, 128, 213, 63, 17, 240, 250, 87, 212, 176, 210, 6, 195, 189, 36, 61, 236, 73, 172, 55, 52, 182, 130, 152, 220, 157, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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