Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ba657d809d55f3cce56855b49587080f899adc557278ec2af5523205995df30

Tx prefix hash: b1433e0365ceebaa8e7ed6e4ce57a7c592e695017fd3e9d7249fb72699945401
Tx public key: ed2b8d397069a4c91dee26728e7ac501e5e3964d1b3db57df62e43a95dc861db
Timestamp: 1750220177 Timestamp [UCT]: 2025-06-18 04:16:17 Age [y:d:h:m:s]: 00:155:18:10:27
Block: 1307407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109123 RingCT/type: yes/0
Extra: 01ed2b8d397069a4c91dee26728e7ac501e5e3964d1b3db57df62e43a95dc861db021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e08861e350af9f372e3080de3989776f94c6062847946c6ecf7a51a5286cd43 0.600000000000 1795018 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": 1307417, "vin": [ { "gen": { "height": 1307407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e08861e350af9f372e3080de3989776f94c6062847946c6ecf7a51a5286cd43" } } ], "extra": [ 1, 237, 43, 141, 57, 112, 105, 164, 201, 29, 238, 38, 114, 142, 122, 197, 1, 229, 227, 150, 77, 27, 61, 181, 125, 246, 46, 67, 169, 93, 200, 97, 219, 2, 17, 0, 0, 0, 2, 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