Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32b2714735f58f8ecd348f91d816e778e7128744fa144e1435acfe7d46edd1cc

Tx prefix hash: 8b0b96822416b0f460196cc9e649dafa98534f4e9f22a662b3a34dc138dbc65a
Tx public key: 704f15af7e9f84a1aae096771c41a3324ea9d345a085d4f23db8141db176daa2
Timestamp: 1760894743 Timestamp [UCT]: 2025-10-19 17:25:43 Age [y:d:h:m:s]: 00:065:06:40:46
Block: 1393488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46712 RingCT/type: yes/0
Extra: 01704f15af7e9f84a1aae096771c41a3324ea9d345a085d4f23db8141db176daa2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e24b997d8ce050b245b2eac7b1007465c58c6f812e1b2329de77cde347cf15d1 0.600000000000 1881753 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": 1393498, "vin": [ { "gen": { "height": 1393488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e24b997d8ce050b245b2eac7b1007465c58c6f812e1b2329de77cde347cf15d1" } } ], "extra": [ 1, 112, 79, 21, 175, 126, 159, 132, 161, 170, 224, 150, 119, 28, 65, 163, 50, 78, 169, 211, 69, 160, 133, 212, 242, 61, 184, 20, 29, 177, 118, 218, 162, 2, 17, 0, 0, 0, 1, 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