Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeda4102e96c75d3e62cd6fa9641c890ba3a7d12e2045aebad8d4cf5240b0dfb

Tx prefix hash: 434d67218ad7b7bf3ec69dc5e98b3aa3862d39adfb3e87c5ec6a186781d7d6f8
Tx public key: 2887d27b71357a69f198da79d9409b80ecf550bc8fb0587c5989f35f8841fce9
Timestamp: 1703963894 Timestamp [UCT]: 2023-12-30 19:18:14 Age [y:d:h:m:s]: 01:078:08:35:57
Block: 924596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317133 RingCT/type: yes/0
Extra: 012887d27b71357a69f198da79d9409b80ecf550bc8fb0587c5989f35f8841fce90211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 405f6461b43ea21963acbd666e76e5015f5c1a6f2fe792c0fb9cedcaad55b44f 0.600000000000 1382352 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": 924606, "vin": [ { "gen": { "height": 924596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "405f6461b43ea21963acbd666e76e5015f5c1a6f2fe792c0fb9cedcaad55b44f" } } ], "extra": [ 1, 40, 135, 210, 123, 113, 53, 122, 105, 241, 152, 218, 121, 217, 64, 155, 128, 236, 245, 80, 188, 143, 176, 88, 124, 89, 137, 243, 95, 136, 65, 252, 233, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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