Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105f4426317db430e57870e5d765849608a6c9f3247abb7e5965a90d3ae31c59

Tx prefix hash: 111f6d2f6752bb83841ec62c41b78dacfd002fa3e5e5175aa90ef0035587d697
Tx public key: 35793da4f6f57df1da60fb0c3d5e3cdd2a3a3041a173ce081cf6420724b9f88f
Timestamp: 1736949212 Timestamp [UCT]: 2025-01-15 13:53:32 Age [y:d:h:m:s]: 00:153:17:38:37
Block: 1197922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109578 RingCT/type: yes/0
Extra: 0135793da4f6f57df1da60fb0c3d5e3cdd2a3a3041a173ce081cf6420724b9f88f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bee31bf1e215ecf665a4966cad1d096dc217930a528ba0d8d7c96ca31fe65f1d 0.600000000000 1684539 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": 1197932, "vin": [ { "gen": { "height": 1197922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bee31bf1e215ecf665a4966cad1d096dc217930a528ba0d8d7c96ca31fe65f1d" } } ], "extra": [ 1, 53, 121, 61, 164, 246, 245, 125, 241, 218, 96, 251, 12, 61, 94, 60, 221, 42, 58, 48, 65, 161, 115, 206, 8, 28, 246, 66, 7, 36, 185, 248, 143, 2, 17, 0, 0, 0, 2, 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