Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 203996b387dc9efc7fce6fc56a6fab08b2d6cc1f48cc8bb02418d5a1368b7671

Tx prefix hash: e70ce078e49a5c9c81f2bf7d947be249ed5f185e78fb40e5ae2f15328d6f01ef
Tx public key: 98f4ab26d47210e9df6976683004f3d3ebc06345abbdfb4e82f38ba52ff3ffa0
Timestamp: 1732432057 Timestamp [UCT]: 2024-11-24 07:07:37 Age [y:d:h:m:s]: 00:358:14:57:48
Block: 1160523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253851 RingCT/type: yes/0
Extra: 0198f4ab26d47210e9df6976683004f3d3ebc06345abbdfb4e82f38ba52ff3ffa0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96e7e86342a1eb6173f3843ef09a8a30bf3ebfadc4f1f82b5367ef49084dd12d 0.600000000000 1646170 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": 1160533, "vin": [ { "gen": { "height": 1160523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96e7e86342a1eb6173f3843ef09a8a30bf3ebfadc4f1f82b5367ef49084dd12d" } } ], "extra": [ 1, 152, 244, 171, 38, 212, 114, 16, 233, 223, 105, 118, 104, 48, 4, 243, 211, 235, 192, 99, 69, 171, 189, 251, 78, 130, 243, 139, 165, 47, 243, 255, 160, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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