Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e486b570c13dd8ee67e67f80ef956cea8c65bccb601a9cbd61b5c88cb22be288

Tx prefix hash: 61ea2acccea77f72264a5dea7096a65ad616e9e8e0da06a064cba12716e81f2f
Tx public key: 26d0bfdd74e0727575aeaa96980c6a9c432f50ec55bd238cc843655d3e1708d1
Timestamp: 1735206004 Timestamp [UCT]: 2024-12-26 09:40:04 Age [y:d:h:m:s]: 00:085:13:48:17
Block: 1183506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60932 RingCT/type: yes/0
Extra: 0126d0bfdd74e0727575aeaa96980c6a9c432f50ec55bd238cc843655d3e1708d10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c523a126ca099b33d9b0ed5adc766ee497ddac26438ab85af9f90be5f8567fb 0.600000000000 1669951 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": 1183516, "vin": [ { "gen": { "height": 1183506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c523a126ca099b33d9b0ed5adc766ee497ddac26438ab85af9f90be5f8567fb" } } ], "extra": [ 1, 38, 208, 191, 221, 116, 224, 114, 117, 117, 174, 170, 150, 152, 12, 106, 156, 67, 47, 80, 236, 85, 189, 35, 140, 200, 67, 101, 93, 62, 23, 8, 209, 2, 17, 0, 0, 0, 3, 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