Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747b585128315fcc7ec18c2cf9419f71e8c307e4211589093944308a32c0e253

Tx prefix hash: 54e7eb89ec9aa2ec300d8e11516f7a1bf0edfea5f29f74c8d0cc471ee6f25ec8
Tx public key: 7d6e45ba91370fc294bbd5361641eb5c6e9ef8bd24374f18ade01d9b9f185094
Timestamp: 1750548787 Timestamp [UCT]: 2025-06-21 23:33:07 Age [y:d:h:m:s]: 00:144:14:11:23
Block: 1310067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101196 RingCT/type: yes/0
Extra: 017d6e45ba91370fc294bbd5361641eb5c6e9ef8bd24374f18ade01d9b9f185094021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60e9c732375420287f5b7f9456d1bb4ff2ec161bfdc22f3be68d159c52d1eb91 0.600000000000 1797684 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": 1310077, "vin": [ { "gen": { "height": 1310067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60e9c732375420287f5b7f9456d1bb4ff2ec161bfdc22f3be68d159c52d1eb91" } } ], "extra": [ 1, 125, 110, 69, 186, 145, 55, 15, 194, 148, 187, 213, 54, 22, 65, 235, 92, 110, 158, 248, 189, 36, 55, 79, 24, 173, 224, 29, 155, 159, 24, 80, 148, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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