Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2ae4635c5e78711abd1bc7022f0d0d2e6d260a640b4cca07661688910343d07

Tx prefix hash: 9a3d29cfcab635bf8b9145d4576ce4d545061b6ec0e10d1220754367f7e6eff8
Tx public key: 4fd537f230d432c4f6bcd4d51e1a70c1ac20f4ee4beee6471ad4a38284b84fab
Timestamp: 1729165371 Timestamp [UCT]: 2024-10-17 11:42:51 Age [y:d:h:m:s]: 00:148:07:21:58
Block: 1133546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105774 RingCT/type: yes/0
Extra: 014fd537f230d432c4f6bcd4d51e1a70c1ac20f4ee4beee6471ad4a38284b84fab0211000000063cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab26770e758ca157ace7ddb1e360b5eb9a742059e1d4bf5880bda7529a15839f 0.600000000000 1616673 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": 1133556, "vin": [ { "gen": { "height": 1133546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab26770e758ca157ace7ddb1e360b5eb9a742059e1d4bf5880bda7529a15839f" } } ], "extra": [ 1, 79, 213, 55, 242, 48, 212, 50, 196, 246, 188, 212, 213, 30, 26, 112, 193, 172, 32, 244, 238, 75, 238, 230, 71, 26, 212, 163, 130, 132, 184, 79, 171, 2, 17, 0, 0, 0, 6, 60, 208, 252, 6, 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