Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc89db967c28d431b36179caa75fbfbcf8245e35cbe91126e0e83ed4fd05f1d5

Tx prefix hash: 58da550f46c100aac07128b1aa00bd4aa3b5b95d25e7b7feafbdd9515476c811
Tx public key: 037534be6ac36c6a391943be8e6469ca988b1fd503759aede87be2dcbeeadfef
Timestamp: 1577908242 Timestamp [UCT]: 2020-01-01 19:50:42 Age [y:d:h:m:s]: 05:070:07:03:14
Block: 36570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200119 RingCT/type: yes/0
Extra: 01037534be6ac36c6a391943be8e6469ca988b1fd503759aede87be2dcbeeadfef021100000010c5b5978f000000000000000000

1 output(s) for total of 464.332691861000 dcy

stealth address amount amount idx
00: 7b75249f388f8e1fff42ca93f35bff69d45c3d054c1dc3305b61e742299475ce 464.332691861000 61979 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": 36580, "vin": [ { "gen": { "height": 36570 } } ], "vout": [ { "amount": 464332691861, "target": { "key": "7b75249f388f8e1fff42ca93f35bff69d45c3d054c1dc3305b61e742299475ce" } } ], "extra": [ 1, 3, 117, 52, 190, 106, 195, 108, 106, 57, 25, 67, 190, 142, 100, 105, 202, 152, 139, 31, 213, 3, 117, 154, 237, 232, 123, 226, 220, 190, 234, 223, 239, 2, 17, 0, 0, 0, 16, 197, 181, 151, 143, 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