Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eaeb3b2d3e84d5081bc53a2ab662d0d7e3d11a3d9768285a1764406bf569fbc

Tx prefix hash: ff8a202b0104ef580546d7a82c017a88a7414cccaf5863487fb279a69de85230
Tx public key: f26dcdf9f02ff1b192e03533c11e157c4bdd94ae5bb28127b47d8d98e7fc47ed
Timestamp: 1756058659 Timestamp [UCT]: 2025-08-24 18:04:19 Age [y:d:h:m:s]: 00:093:20:45:57
Block: 1353573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67030 RingCT/type: yes/0
Extra: 01f26dcdf9f02ff1b192e03533c11e157c4bdd94ae5bb28127b47d8d98e7fc47ed0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d168f4bf814697b80a8e09d590672157c8b54a2f83cf37231cf0717e09b1fa4c 0.600000000000 1841550 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": 1353583, "vin": [ { "gen": { "height": 1353573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d168f4bf814697b80a8e09d590672157c8b54a2f83cf37231cf0717e09b1fa4c" } } ], "extra": [ 1, 242, 109, 205, 249, 240, 47, 241, 177, 146, 224, 53, 51, 193, 30, 21, 124, 75, 221, 148, 174, 91, 178, 129, 39, 180, 125, 141, 152, 231, 252, 71, 237, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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