Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 372e567429068f4a7e973f521d4615270ba1db8f6af2d39cb8a6a0c8f52bc76f

Tx prefix hash: 7c22ca1e3a672644cd6b67d320be48bfa173a62799e0d472025aa0b4c02c0733
Tx public key: 807220316f3b025effcdfea61b4a420490a4d53803dc9e1ff24d6b9527d85b0a
Timestamp: 1761557159 Timestamp [UCT]: 2025-10-27 09:25:59 Age [y:d:h:m:s]: 00:057:14:18:23
Block: 1398976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41219 RingCT/type: yes/0
Extra: 01807220316f3b025effcdfea61b4a420490a4d53803dc9e1ff24d6b9527d85b0a02110000000525a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2420b8ef0af277d0e9ca28767a5e7c64ee2238a1784a53952fa392885549d3a1 0.600000000000 1887279 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": 1398986, "vin": [ { "gen": { "height": 1398976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2420b8ef0af277d0e9ca28767a5e7c64ee2238a1784a53952fa392885549d3a1" } } ], "extra": [ 1, 128, 114, 32, 49, 111, 59, 2, 94, 255, 205, 254, 166, 27, 74, 66, 4, 144, 164, 213, 56, 3, 220, 158, 31, 242, 77, 107, 149, 39, 216, 91, 10, 2, 17, 0, 0, 0, 5, 37, 163, 90, 15, 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