Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b61f0d925242e515ad9e2709a57ca518fac856e64b407a6ba9177e32cb3b52f

Tx prefix hash: f080ef09eada20037686af5a0c7207a29deb3762e6f736514b663870905d72df
Tx public key: 0d92f02936eef18647392be2c9919120abe4f9a7a5a5618dc5cae4823f2c09ce
Timestamp: 1754444112 Timestamp [UCT]: 2025-08-06 01:35:12 Age [y:d:h:m:s]: 00:011:16:55:43
Block: 1341159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7513 RingCT/type: yes/0
Extra: 010d92f02936eef18647392be2c9919120abe4f9a7a5a5618dc5cae4823f2c09ce0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7401f4a19607c73f58f5b129df19d72f4d2cee7dcb2119563c62953c03b03eec 0.600000000000 1828982 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": 1341169, "vin": [ { "gen": { "height": 1341159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7401f4a19607c73f58f5b129df19d72f4d2cee7dcb2119563c62953c03b03eec" } } ], "extra": [ 1, 13, 146, 240, 41, 54, 238, 241, 134, 71, 57, 43, 226, 201, 145, 145, 32, 171, 228, 249, 167, 165, 165, 97, 141, 197, 202, 228, 130, 63, 44, 9, 206, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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