Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58829e6bbe5bfd510d9fe1185fce4421b1b82b058532702ee0f3cccccc99ff15

Tx prefix hash: 3d92b39ad16928ad08bc7af44b39e6a4b3e8a2c87399227d60356d3dba5973a2
Tx public key: dd1a4a6f7151a7f1be54b723c339998ba73aa98b9ad49cf910ed4da41da6419c
Timestamp: 1751663781 Timestamp [UCT]: 2025-07-04 21:16:21 Age [y:d:h:m:s]: 00:132:11:36:05
Block: 1318855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92985 RingCT/type: yes/0
Extra: 01dd1a4a6f7151a7f1be54b723c339998ba73aa98b9ad49cf910ed4da41da6419c02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1783b0e1e37c6ffa09bf52a86a763516b5f37b382bccd71728d0a961f1e2211 0.600000000000 1806542 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": 1318865, "vin": [ { "gen": { "height": 1318855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1783b0e1e37c6ffa09bf52a86a763516b5f37b382bccd71728d0a961f1e2211" } } ], "extra": [ 1, 221, 26, 74, 111, 113, 81, 167, 241, 190, 84, 183, 35, 195, 57, 153, 139, 167, 58, 169, 139, 154, 212, 156, 249, 16, 237, 77, 164, 29, 166, 65, 156, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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