Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d2d2fe0f40c333e74afb5e203958e5c89e46149198df147a31466a853ab942b

Tx prefix hash: 291d5f618ff324942eed22e9bf998c2831e8cf5fe4ab7b4c1c17870986bf6c60
Tx public key: 3e041daaa6f285a3a92461d95a43014bb705bd839b685ebc46e37c5b67b1eb3f
Timestamp: 1750623767 Timestamp [UCT]: 2025-06-22 20:22:47 Age [y:d:h:m:s]: 00:151:18:19:32
Block: 1310665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106348 RingCT/type: yes/0
Extra: 013e041daaa6f285a3a92461d95a43014bb705bd839b685ebc46e37c5b67b1eb3f021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc74144a417678cb70a3551e9adcc130a9691bd7dbc5b0e39f8dd1cfd9ef3a84 0.600000000000 1798286 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": 1310675, "vin": [ { "gen": { "height": 1310665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc74144a417678cb70a3551e9adcc130a9691bd7dbc5b0e39f8dd1cfd9ef3a84" } } ], "extra": [ 1, 62, 4, 29, 170, 166, 242, 133, 163, 169, 36, 97, 217, 90, 67, 1, 75, 183, 5, 189, 131, 155, 104, 94, 188, 70, 227, 124, 91, 103, 177, 235, 63, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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