Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14a760b41f2c0a5ab236ee73753ae1c222d3ab341aa31fbd274a49e74ef59ca4

Tx prefix hash: 0a1b936677cd11e9ae2b63ac444fa4f54ad94f35e11e83a13ebec1e39de6b07b
Tx public key: 79c814a53d41406df6a3e9503c20a470de7e826fc01d3076e987f760b79ad2aa
Timestamp: 1681201421 Timestamp [UCT]: 2023-04-11 08:23:41 Age [y:d:h:m:s]: 01:320:00:58:22
Block: 736132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489991 RingCT/type: yes/0
Extra: 0179c814a53d41406df6a3e9503c20a470de7e826fc01d3076e987f760b79ad2aa0211000000035029cbac000000000000000000

1 output(s) for total of 2.233003093000 dcy

stealth address amount amount idx
00: e5fb026fe9c00a3c0a993c5be6f0e825b0e4d8b2f6725a752f2efb132438f42e 2.233003093000 1182531 of 0

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": 736142, "vin": [ { "gen": { "height": 736132 } } ], "vout": [ { "amount": 2233003093, "target": { "key": "e5fb026fe9c00a3c0a993c5be6f0e825b0e4d8b2f6725a752f2efb132438f42e" } } ], "extra": [ 1, 121, 200, 20, 165, 61, 65, 64, 109, 246, 163, 233, 80, 60, 32, 164, 112, 222, 126, 130, 111, 192, 29, 48, 118, 233, 135, 247, 96, 183, 154, 210, 170, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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