Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8a7d4df154a7060c5c270710e277d92df10f2bf76b1aca9d2058972f7b8f39a

Tx prefix hash: 03dfc09ecac7766241b29e9858e5c08c6d102efd2e2f0b6d73393bbdd47f5ecd
Tx public key: a53de85f214f23a1d5c1c6914d8a26588016e571a411dc927ae8ac07291ab189
Timestamp: 1751122699 Timestamp [UCT]: 2025-06-28 14:58:19 Age [y:d:h:m:s]: 00:142:18:49:11
Block: 1314584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100140 RingCT/type: yes/0
Extra: 01a53de85f214f23a1d5c1c6914d8a26588016e571a411dc927ae8ac07291ab18902110000000843846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62004a68d1fe4ab6b23fce95177d05aa5ea107a7b1693b8f9a55ee3c09ff9fae 0.600000000000 1802233 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": 1314594, "vin": [ { "gen": { "height": 1314584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62004a68d1fe4ab6b23fce95177d05aa5ea107a7b1693b8f9a55ee3c09ff9fae" } } ], "extra": [ 1, 165, 61, 232, 95, 33, 79, 35, 161, 213, 193, 198, 145, 77, 138, 38, 88, 128, 22, 229, 113, 164, 17, 220, 146, 122, 232, 172, 7, 41, 26, 177, 137, 2, 17, 0, 0, 0, 8, 67, 132, 109, 102, 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