Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f0248d42784004de3bcf040354bab3d9bb91e610b0bc7c3af861d99fded4e1e

Tx prefix hash: 3822d4352de8b56d8239e06c2c7e832988adae8bce30697909a0b3ace56cb08e
Tx public key: 8ae88080f9537084b1ccf8ca83c232e89e5de03c83a7a92fd2792e76e09c4cc1
Timestamp: 1755457011 Timestamp [UCT]: 2025-08-17 18:56:51 Age [y:d:h:m:s]: 00:044:00:27:00
Block: 1348682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31235 RingCT/type: yes/0
Extra: 018ae88080f9537084b1ccf8ca83c232e89e5de03c83a7a92fd2792e76e09c4cc10211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f04e8db5a4f6ab5ae17269f103ce7c45079d25eeeaab1515a1a09945b7d38d4 0.600000000000 1836609 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": 1348692, "vin": [ { "gen": { "height": 1348682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f04e8db5a4f6ab5ae17269f103ce7c45079d25eeeaab1515a1a09945b7d38d4" } } ], "extra": [ 1, 138, 232, 128, 128, 249, 83, 112, 132, 177, 204, 248, 202, 131, 194, 50, 232, 158, 93, 224, 60, 131, 167, 169, 47, 210, 121, 46, 118, 224, 156, 76, 193, 2, 17, 0, 0, 0, 2, 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