Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fcd60f0ed4cc38450d087684406a8f0a9f4f7aa782dfe17a97eb4876eeb35f9

Tx prefix hash: b9371b9cb424fb3f466a6cdcd496265e7cb99f91109c9bf2976b3c543b6cc040
Tx public key: 4c9b739b106c79ea6f7d218b501c1a57709ef50c09f790865cd37bf0ffa2ad11
Timestamp: 1754662849 Timestamp [UCT]: 2025-08-08 14:20:49 Age [y:d:h:m:s]: 00:097:14:25:09
Block: 1342872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68840 RingCT/type: yes/0
Extra: 014c9b739b106c79ea6f7d218b501c1a57709ef50c09f790865cd37bf0ffa2ad11021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0a99e73e030baf9492b94411b9ff8819e47a4e1855311ecb10aee1f137037a7 0.600000000000 1830705 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": 1342882, "vin": [ { "gen": { "height": 1342872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0a99e73e030baf9492b94411b9ff8819e47a4e1855311ecb10aee1f137037a7" } } ], "extra": [ 1, 76, 155, 115, 155, 16, 108, 121, 234, 111, 125, 33, 139, 80, 28, 26, 87, 112, 158, 245, 12, 9, 247, 144, 134, 92, 211, 123, 240, 255, 162, 173, 17, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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