Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 265dec72a799a40d0ac40ad1401d921ac63b33cf6dc5c61bae2b9ada618656a0

Tx prefix hash: be87a23a77f11a4d15eb881d95ff27395e2d8674e969f320673c949da7a55afe
Tx public key: a6d3e4f7911cb21dbdef30e824271d225740ec8a31ad232e9d1b3d3f565df016
Timestamp: 1757944583 Timestamp [UCT]: 2025-09-15 13:56:23 Age [y:d:h:m:s]: 00:136:13:52:18
Block: 1369026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97613 RingCT/type: yes/0
Extra: 01a6d3e4f7911cb21dbdef30e824271d225740ec8a31ad232e9d1b3d3f565df016021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72a0c04849f862c6477d9c5cbb0c17c7e555d847e155e66a8f91bb313a35c364 0.600000000000 1857095 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": 1369036, "vin": [ { "gen": { "height": 1369026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72a0c04849f862c6477d9c5cbb0c17c7e555d847e155e66a8f91bb313a35c364" } } ], "extra": [ 1, 166, 211, 228, 247, 145, 28, 178, 29, 189, 239, 48, 232, 36, 39, 29, 34, 87, 64, 236, 138, 49, 173, 35, 46, 157, 27, 61, 63, 86, 93, 240, 22, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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