Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc79d03ceb3086cfc63266e42ada7676390dd4088d5d0616d2f037cb8f4d997

Tx prefix hash: 3f03c916cb8d54375c192d54b945f2c4212d94f26bf9b2b3f8bddfe5d206b625
Tx public key: a88d055493d2c79dc320dc929c52639e9856e651b4caab6eb29785257593bc35
Timestamp: 1574130005 Timestamp [UCT]: 2019-11-19 02:20:05 Age [y:d:h:m:s]: 05:001:11:11:09
Block: 12345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1144068 RingCT/type: yes/0
Extra: 01a88d055493d2c79dc320dc929c52639e9856e651b4caab6eb29785257593bc35021100000001ccefb800000000000000000000

1 output(s) for total of 558.594658372000 dcy

stealth address amount amount idx
00: 969487391f0f5be551b541cee2fbb0e4c57d3dd1e83f432101b02dc015d05231 558.594658372000 13540 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": 12355, "vin": [ { "gen": { "height": 12345 } } ], "vout": [ { "amount": 558594658372, "target": { "key": "969487391f0f5be551b541cee2fbb0e4c57d3dd1e83f432101b02dc015d05231" } } ], "extra": [ 1, 168, 141, 5, 84, 147, 210, 199, 157, 195, 32, 220, 146, 156, 82, 99, 158, 152, 86, 230, 81, 180, 202, 171, 110, 178, 151, 133, 37, 117, 147, 188, 53, 2, 17, 0, 0, 0, 1, 204, 239, 184, 0, 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