Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56536b648199e7a69f6ce2a67e07dd41df1f86bceead3957b8740aabd43e2300

Tx prefix hash: 7c1ff130eb54e60429d658348c9068c2a649f476400171caf1d71141a15c27d6
Tx public key: adc07f86753cb7c7bc0fd7bae8c0d45c83a1d0d7e379f4123814c21c84f4cf01
Timestamp: 1579272277 Timestamp [UCT]: 2020-01-17 14:44:37 Age [y:d:h:m:s]: 04:346:23:27:23
Block: 47636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137418 RingCT/type: yes/0
Extra: 01adc07f86753cb7c7bc0fd7bae8c0d45c83a1d0d7e379f4123814c21c84f4cf010211000000098a2ee0d9000000000000000000

1 output(s) for total of 426.747017169000 dcy

stealth address amount amount idx
00: 5a6c7671b9d961fa57e57b8d9b05382913ba2f9e7f4090eebe4012a802daf79e 426.747017169000 88020 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": 47646, "vin": [ { "gen": { "height": 47636 } } ], "vout": [ { "amount": 426747017169, "target": { "key": "5a6c7671b9d961fa57e57b8d9b05382913ba2f9e7f4090eebe4012a802daf79e" } } ], "extra": [ 1, 173, 192, 127, 134, 117, 60, 183, 199, 188, 15, 215, 186, 232, 192, 212, 92, 131, 161, 208, 215, 227, 121, 244, 18, 56, 20, 194, 28, 132, 244, 207, 1, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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