Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398766c3cb99a8ab4e71a7ce91b0023af98e67aa4ca120024e58647fe8d287c8

Tx prefix hash: 59272b94d662fff85d5e90fe8935f707e8cfc7b9c137e37964250482cddc4a60
Tx public key: 4e6bf9579f4dbf4b0a24475e654b4e016812ac82c0c64f8ea6a751dc3ada904f
Timestamp: 1755910539 Timestamp [UCT]: 2025-08-23 00:55:39 Age [y:d:h:m:s]: 00:090:07:52:06
Block: 1352348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64480 RingCT/type: yes/0
Extra: 014e6bf9579f4dbf4b0a24475e654b4e016812ac82c0c64f8ea6a751dc3ada904f0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f79af4c09d62338ee0d7d8abcd0753f28e4e681a24fb15e465385fcbd22a0be 0.600000000000 1840311 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": 1352358, "vin": [ { "gen": { "height": 1352348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f79af4c09d62338ee0d7d8abcd0753f28e4e681a24fb15e465385fcbd22a0be" } } ], "extra": [ 1, 78, 107, 249, 87, 159, 77, 191, 75, 10, 36, 71, 94, 101, 75, 78, 1, 104, 18, 172, 130, 192, 198, 79, 142, 166, 167, 81, 220, 58, 218, 144, 79, 2, 17, 0, 0, 0, 4, 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