Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 927e10342c50395de63a91b3b208b79a02037c9400aecf22d33a19d9b78154a1

Tx prefix hash: d7a4e50080fa7a01a9ead1fbc6acb7e4d7e305b6900ac322ac404c1d86684cc0
Tx public key: fdc18b222ed4bbcc19f93c2687d277907af19cb38843f0c035df96f5bf26d9c4
Timestamp: 1751344639 Timestamp [UCT]: 2025-07-01 04:37:19 Age [y:d:h:m:s]: 00:138:17:36:55
Block: 1316311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97358 RingCT/type: yes/0
Extra: 01fdc18b222ed4bbcc19f93c2687d277907af19cb38843f0c035df96f5bf26d9c4021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ce72219862966c367e07b929be9f8736932cbe51afdf8ca9500f1695fdc6175 0.600000000000 1803970 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": 1316321, "vin": [ { "gen": { "height": 1316311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ce72219862966c367e07b929be9f8736932cbe51afdf8ca9500f1695fdc6175" } } ], "extra": [ 1, 253, 193, 139, 34, 46, 212, 187, 204, 25, 249, 60, 38, 135, 210, 119, 144, 122, 241, 156, 179, 136, 67, 240, 192, 53, 223, 150, 245, 191, 38, 217, 196, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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