Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5728c298fa6fbfba1aebfc37405f4f45c4cac1039858d12083d0b3e080667d5b

Tx prefix hash: 6fc0bdb2590b958d9af28b4b717179bb4caf73eca9f8c772cb49c934ee3c6424
Tx public key: 22c00ae6560aaeeddde5b2e53e6a4332d8fff0317bb0e43a20738c0243b20b2e
Timestamp: 1765924024 Timestamp [UCT]: 2025-12-16 22:27:04 Age [y:d:h:m:s]: 00:017:15:28:52
Block: 1435145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12646 RingCT/type: yes/0
Extra: 0122c00ae6560aaeeddde5b2e53e6a4332d8fff0317bb0e43a20738c0243b20b2e0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fea7afa4ac6f95e388c9f670f02399322f13fb2717ca597b064e7bddbacfdf08 0.600000000000 1923942 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": 1435155, "vin": [ { "gen": { "height": 1435145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fea7afa4ac6f95e388c9f670f02399322f13fb2717ca597b064e7bddbacfdf08" } } ], "extra": [ 1, 34, 192, 10, 230, 86, 10, 174, 237, 221, 229, 178, 229, 62, 106, 67, 50, 216, 255, 240, 49, 123, 176, 228, 58, 32, 115, 140, 2, 67, 178, 11, 46, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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