Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e8a2e22af36d24b86e18be9cb99a8ae7139fe1900031de568aa10b23284371

Tx prefix hash: 6002a5e529beaa4683948b1b8b7261aaa993b1244741b7549d25c9d0a50f29d3
Tx public key: 748336e59c9523eae0d281af4b726ef69f4d90296ae3a3797f8c28b697dd87d5
Timestamp: 1652207173 Timestamp [UCT]: 2022-05-10 18:26:13 Age [y:d:h:m:s]: 02:311:08:30:10
Block: 498164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742810 RingCT/type: yes/0
Extra: 01748336e59c9523eae0d281af4b726ef69f4d90296ae3a3797f8c28b697dd87d50211000000022e6b1fd5000000000000000000

1 output(s) for total of 13.720693991000 dcy

stealth address amount amount idx
00: dcb88411f0d8d21226407e8d56c0e58f7f78d735233a5d1808b079d48c23768d 13.720693991000 922339 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": 498174, "vin": [ { "gen": { "height": 498164 } } ], "vout": [ { "amount": 13720693991, "target": { "key": "dcb88411f0d8d21226407e8d56c0e58f7f78d735233a5d1808b079d48c23768d" } } ], "extra": [ 1, 116, 131, 54, 229, 156, 149, 35, 234, 224, 210, 129, 175, 75, 114, 110, 246, 159, 77, 144, 41, 106, 227, 163, 121, 127, 140, 40, 182, 151, 221, 135, 213, 2, 17, 0, 0, 0, 2, 46, 107, 31, 213, 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