Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55871fc23977cbbb7f4df8ca94532b24a8373c5bfa7f03fab3cb3d9bc317658f

Tx prefix hash: e975f8367edc50d964e73c9a26246d659aabdfd4491df73763a442eadd85a2b0
Tx public key: ccc542e51e3e006b38afc080ec909f7fa67009d8ffc965f2fefe5c06518e1511
Timestamp: 1744904289 Timestamp [UCT]: 2025-04-17 15:38:09 Age [y:d:h:m:s]: 00:025:05:02:02
Block: 1263509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18040 RingCT/type: yes/0
Extra: 01ccc542e51e3e006b38afc080ec909f7fa67009d8ffc965f2fefe5c06518e1511021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ee8d17eabf0133a2df381b4706e00704fb6aa9aacd869ca9e1f120e3d46756f 0.600000000000 1750700 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": 1263519, "vin": [ { "gen": { "height": 1263509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ee8d17eabf0133a2df381b4706e00704fb6aa9aacd869ca9e1f120e3d46756f" } } ], "extra": [ 1, 204, 197, 66, 229, 30, 62, 0, 107, 56, 175, 192, 128, 236, 144, 159, 127, 166, 112, 9, 216, 255, 201, 101, 242, 254, 254, 92, 6, 81, 142, 21, 17, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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