Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35376e0470fa229d162486272464f4b246cc4b5bc9c0d45108d595d41c097bf7

Tx prefix hash: 6b137b43d501eb457dac6fc59dcc12420d37e3b5bc279729b29e360c5abbd9ff
Tx public key: 5e8fdeec33bb2eb4338dfed527e42fb67c173f4a5369c14b30cf2022d4caa028
Timestamp: 1736094289 Timestamp [UCT]: 2025-01-05 16:24:49 Age [y:d:h:m:s]: 00:088:09:32:54
Block: 1190861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62939 RingCT/type: yes/0
Extra: 015e8fdeec33bb2eb4338dfed527e42fb67c173f4a5369c14b30cf2022d4caa0280211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58879106d5d8f7954ccce36e1e163509e3f384a9c937d6d6b1ad4a3a3729c879 0.600000000000 1677382 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": 1190871, "vin": [ { "gen": { "height": 1190861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58879106d5d8f7954ccce36e1e163509e3f384a9c937d6d6b1ad4a3a3729c879" } } ], "extra": [ 1, 94, 143, 222, 236, 51, 187, 46, 180, 51, 141, 254, 213, 39, 228, 47, 182, 124, 23, 63, 74, 83, 105, 193, 75, 48, 207, 32, 34, 212, 202, 160, 40, 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